perm filename NOTE.RHT[SYS,HE] blob
sn#128408 filedate 1974-11-07 generic text, type T, neo UTF8
∂07-NOV-74 1226 HAL,RHT
Dunno. It will depend on how theparser/scanner is finally implemented.
Most likely just like SAIL's. However, I'm not sure it really makes
much difference or that we should say much about it in the report,
since text macros aren't really part of the language. (I.e. almost
any text preprocessor can be used). On the other hand, we do mention that
they are going to be available, so perhaps we should say something.
How about:
DEFINE foo(a,b,c) "⊂⊃" = ⊂ body ⊃;
for macro definition, &
foo(a,b,c)
for call. Also, we will most likely try to win with "nesting" pairs
like ⊂⊃()[]{}.
I'm still working on the ct structs. Turned out to be a big revision.
Russ